Glad you like the idea. Take your time. :)
I'm only watching the three plugins you mentioned in 'Info
Extensions':
* Rate: A rating extension to check rating scores logged as info
vars.
* Tags: An info var tag system.
* SearchPlus: One or more advanced search features. Still thinking
about all the options for using this thing!
http://boltwire.com/index.php?p=resources.solutions.info
:)
Cheers,
linly
On Sep 7, 7:37 pm, "The Editor" <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 6, 2008 at 1:36 PM, Linly <[EMAIL PROTECTED]> wrote:
>
> > The ability of recognizing 'lines' is one of the powerful feature in
> > BoltWire. The /=[(include)]=/ can find a certain line and output it,
> > the 'log' command can add, delete, sort lines, the 'action.undo' can
> > find the diff between different versions...
>
> > So if we think further, can we treat 'line' as an item or, more
> > technical, an object?
>
> > If we have line object, we can edit a line, delete a line, show/hide a
> > line, add a (line level) data value to a line... A line object makes
> > many thing easier and faster.
>
> > 1) Using line data makes sorting more flexible and faster;
> > 2) Edit-in-place would be easy;
> > 3) Easily write photo description right under the photo (not under the
> > wiki markup);
> > 4) Possibly moving line object up and down by hand?
>
> > Is this a good idea or ...
>
> I think this could be a very useful feature, and I'm inclined to try
> adding it... It might be a bit tricky however, and it would take some
> time for me to get around to it as I'm very busy right at the moment.
>
> What I'm thinking was a special facility in the edit command that
> allows you to specify a target like some.page::3
> (ie. replace line three with edit content). This uses the :: markup
> we've come to associate with info variables (text variables, or
> perhaps we could call them line variables...
>
> The problem with this is you have to know which line something is--and
> there's no visible marker system. Of course we could add a function
> like [(getline "some text to match" target=some.page)] which could be
> used in forms to indicate which line to replace. That would be easy
> enough.
>
> Another option might be a special way to mark info variables so that
> the field is not visible. Kind of like a mini anchor. Perhaps:
>
> visiblefield: some text
> :hiddenfield: some other text
>
> This would display in the page as
>
> visiblefield: some text
> some other text
>
> But we could use our new info variable capabilities to replace either
> line without having to add any special code. And it seems it might be
> easier to setup forms for editing if you could easily control which
> line is being edited.
>
> I should add, of the four possible uses you mentioned, #2 would be
> doable, and probably #4, but I'm not so sure about #1 or #4 being
> possible without adding additional code of some kind.
>
> Good idea linly! I'll add these to the roadmap so we can add them at
> some point.
>
> Cheers,
> Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
