I'll wait and see what others think of it. And yes, some very specific
parts of freemind, by my opinion did seem to get overly feature-heavy
:( But I'm sure we can all fix things up later, maybe after 0.9.0.
And I think I completely missed the development of the extension
interfaces, and since those things are usually pretty well-hidden from
normal interfaces, it is hard for me to get a grip on what's being offered
there or what are the features. Some references/pointers to more info
could be very appreciated.
Another thing about the HTML editor I noticed was this:
When I change the font size of a particular bit in the Layout view, all is
well. When I make the same change in HTML view and then switch back to
Layout, all seems well. But when I move the cursor onto the changed-sized
text, the font-size indicator does NOT reflect the changed value. I'm not
sure if we can actually fix this from freemind core code alone, or is it
internal to SimplyHTML.
And thanks for the welcome, though unfortunately even I will have my busy
times and my enthusiasm is unlikely to be very consistent :(( But when I
*am* available, I tend to make the most of it
On Tue, 08 Jan 2008 23:24:28 +0600, Ray Benjamin <raybenjamin@...>
> Welcome to the project. Your enthusiasm and energy are admirable. I'm
> glad you've chosen to work with us. I'm especially pleased that you are
> willing to jump right in to fixing problems you encounter.
> I'm Ray Benjamin, self-appointed project nit-picker and cheerleader. My
> background is in QA. Since I joined up, I've done more in the way of
> making suggestions and testing than code writing. Many of us on the
> project have to juggle a lot of responsibilities and other projects, so
> you'll get faster responses from some than others, when you post here.
> I'm using FreeMind to help me write a novel. For me, the writing has to
> come first.
> This is a pretty important time for this project. It looks like there
> may be some big changes made, going forward. We're trying hard to get
> the 0.9.0 release out the door. We're also looking forward towards the
> next release, and considering doing some major refactoring of the core
> code to make it easier to add new functionality to the program.
> From a QA standpoint, I don't think we should be allowing editing of
> the HTML, HEAD, or BODY tags in the note editor. As you point out, it's
> misleading. I propose that the proper solution to the problem is to hide
> those elements, if possible, in the note editor's HTML code view. If we
> want to allow the user to make document wide modifications to those
> elements, that probably should be done from an options or preferences
> menu selection using a pop-up menu.
> I don't think this problem warrants a fix in 0.9.0, since we're trying
> to get 0.9.0 out the door, but i do think it belongs in the next
> release. That's just my personal opinion. Others may have different
> Reasamp wrote:
>> I'm not quites sure who here's working on it right now, so I'm posting
>> When I saw the HTML editor with long notes, impression was that every
>> is a miniature HTML document and just naively I expected that if I make
>> changes inside <style> tags in <head>, it will make "nodewide"
>> changes. Even seemed to work at first. The Layout view changed
>> my actions. But I click OK and all that change simply disappears.
>> Now I have been able to track down the pieces of code involving this,
>> was not the hard part. The thing is I just joined this list the other
>> so I don't really know what's the intended solution. I'd be glad to hear
>> of any options, but the ones I see are:
>> 1) Allow <head> editing. But I'm not sure why this part of HTML was
>> repeatedly and intentionally wiped out in various parts of the code. Is
>> to disable scripting? Or was it this exact problem that was being
>> 2) Disable direct editing of <head> altogether. It would take quite a
>> of patching to allow user-mods in the <head> tag anyway. So one way to
>> the user know that such changes are not supported might be to hide the
>> <head> part of the HTML code altogether, and show only <body>. Or to
>> somehow just disable editing of that part, but i'm not sure SimplyHTML
>> supports "disabling" part of the code from being edited. Don't have much
>> details on how SimplyHTML works.
>> 3) "Node-wide" formatting is too small a scope to be troubled with this
>> "feature". But, a slight change of this behaviour could be considered
>> by some: the <head> part would be considered global across the entire
>> Anyone changes <head>, adds a new class for any tag, would effectively
>> change the head tag for every single node in the map. This would give
>> <style> tags the same usefulness as their website counterparts. Not sure
>> if most ppl will consider it useful or confusing though. Could be used
>> quickly apply a specific combination of formatting to a certain class of
>> Now I just need to know which direction is the intended one. Sorry for
>> length of the mail.
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> Freemind-developer mailing list
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> Freemind-developer mailing list