Some suggestions

[CracKPod]

Hey,
Here are some of my suggestions.

1. Improve the overall looks of the stickwiki. At the moment it's
somehow a little frustrating. A design similiar to the wikipedia would
be great (http://en.wikipedia.org/wiki/Main_Page).

2. Add a new-page Button. At the moment there only is
special::new_page but why won't you add a new page button in the
toolbar, where the other essential things are located aswell, like
editing the page?

3. When creating saving or whatever a page, don't use a popup to
retrieve information like, "Which name should the entry have", simply
let the user edit the title and maybe tick a little box which
indicates if it should be added to the main menue. (Kinda like in a
forum or maybe in TiddlyWiki)

4. Add automatic linking for links in entries. Maybe in form of a pre-
ticked tickbox (Automatically link all pages) or something similiar.
Support for http:// and irc:// should be there. (atleast)

5. Stickwiki "panels" and "elements" better. For example the main menu
isn't on the same high with the content panel.

6. The About information at the bottom of the page: It would be nice
if you kept it simple without the ugly line.

---

I use Ubuntu with Firefox 3.0.1 (Mozilla/5.0 (X11; U; Linux i686; de;
rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1). I always get the
following error when I try to embed a file into the stickwiki:

"
Exception while attempting to load

ReferenceError: ActiveXObject is not defined
Exception while attempting to load

[Exception... "Component returned failure code: 0x80520001
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsILocalFile.initWithPath]"
nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location:
"JS frame :: file:///home/crackpod/Desktop/WoaS/Workspace/woas-0.9.6b.htm
:: mozillaLoadFile :: line 1000" data: no]
Exception while attempting to load

ReferenceError: ActiveXObject is not defined
"

And for the images:

"
Exception while attempting to load

ReferenceError: ActiveXObject is not defined
Exception while attempting to load

[Exception... "Component returned failure code: 0x80520001
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsILocalFile.initWithPath]"
nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location:
"JS frame :: file:///home/crackpod/Desktop/WoaS/Workspace/woas-0.9.6b.htm
:: mozillaLoadFile :: line 1000" data: no]
Exception while attempting to load

ReferenceError: ActiveXObject is not defined
"

[CracKPod]

Srry, a little addition:

Why don't you simply include the debug info in the woas["config"] dict?

[Snaga]

Most of the suggestions you give are CSS-related. If like me you are
a former TiddlyWiki user you will find the WoaS CSS both simpler to
edit and closer to the raw state. TW was kind of elaborate in the way
it approaches things, to the point of being exasperating.

The HR above the About link can be undisplayed with CSS (at least you
could do it in 0.9.5). Legolas said that is just a hack and I agree.
The way the HTML is written you have to make all HR's invisible, not
just one. I think it looks better w/o the HR's regardless.
Alternatively you could change the width of the HR's.

I think your suggestions for the default CSS are good, but you are
talking about esthetic judgments, which when it comes down to it are
up to the developer's sense of what looks good. Which is why we have
an "import CSS also" checkbox.

I have suggested that we should be able (like in TiddlyWiki) to edit
the HTML like we edit CSS. There are several problems with this:
* It's quite an involved process to set up that option in the code,
and other things take priority
* If a user edits the HTML there is a good chance that they could
screw something up
* Most problems with the HTML can be solved with CSS

Now my view is not that we should be able to edit the HTML but that it
should be tightened up, written with a better style, that not only
separates the functions of structure, action, and appearance more
rigorously but makes the page layout more generic, so users like us
can make radical changes to it without difficulty or conflicts.

To clarify, I'd like to see everything in the HTML be a separate DOM
element (HR's are not) and an even simpler layout that won't be hard
to rearrange with CSS. If for example you wanted to put the titles at
the bottom of the page, or make the sidebar disappear or move to the
other side, or display WoaS on a mobile phone...

The fun part of TiddlyWiki was that you could easily (well actually
that's BS, it takes hours) change the colors, icons, layout, whatever,
of the document just by opening pages. WoaS could do much the same
thing by simplifying layout just a little bit, and following the TW
concept of "everything is a tiddler". In other words, everything,
especially the icons, etc., could be an Include::, an editable page.
I don't know if HTML could be treated like that also...

Having said that, I really think the priority right now should be
stability. L. is only one guy, and not too many folks have stepped
forward to help with going to 1.0 (I wish I could). If something like
this is a CSS question, let's be happy with it for now. Making WoaS
more elaborate is IMHO not helpful in the long run. Just learn to
work with it, and you can do just about anything.

Thanks

S

PS I hate to get long-winded but I am using the same setup as you
(8.04, FF3) and here is what I put in the CSS to fix the sidebar
vertical alignment:

div.menu_area {
border-width: 1pt;
/* border-color: grey; */
border-color: #B4C2CB;
border-style: solid;
font-size: 9pt;
background-color: white;
padding: 5pt;
width: 13%;
left: 1%;
/* Alignment for FF3 */
top: 45px;

[CracKPod]

So you are basically saying if I learned HTML, CSS and JavaScript it
shouldn't be a problem to customize the StickWiki to my likings?
Ok, I guess I'll really do it.

CracKPod

[CracKPod]

Something I did notice while taking a look at the source is that
nearly
all functions are located in a dict. woas["function"] = function ()
{} .

Why don't use JavaSript's OOP? Using dict's is (in my opinion) a very
pythonic way
to realize that. And as you already said, the code really needs a big
clean-up and reorganize.