[WV] What is needed to tag an application as available in the WebVelocity 'homepage'?

[Rick Flower]

I've got my Seaside application bundle loaded and
namespaces are good now.. I see 3 of my ~20 packages
listed in the 'available' section of the WV homepage..
I'm not sure why they're listed -- of course none of
them are anything I'm interested in.. Is there a way
to have my application code bundle show up and none
of the internal packages? I didn't find anything
in the WV internal docs on this..

Sorry for asking so many questions...

--
You received this message because you are subscribed to the Google Groups "WebVelocity" group.
To post to this group, send email to webve...@googlegroups.com.
To unsubscribe from this group, send email to webvelocity...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webvelocity?hl=en.

[Michael Lucas-Smith]

On 5/3/10 5:16 PM, Rick Flower wrote:
> I've got my Seaside application bundle loaded and
> namespaces are good now.. I see 3 of my ~20 packages
> listed in the 'available' section of the WV homepage..
> I'm not sure why they're listed -- of course none of
> them are anything I'm interested in.. Is there a way
> to have my application code bundle show up and none
> of the internal packages? I didn't find anything
> in the WV internal docs on this..
>
> Sorry for asking so many questions...
>
>

WV doesn't show bundles at all sorry. When we sat down with some people
and tried to explain what they are and how they work, it quickly became
clear that it was easier to have just the one concept for WV - packages.
We may put some effort in to hiding bundles but providing their same
behavior down the road - but not in 1.0 or 1.1.

Michael

[Rick Flower]

On May 3, 2010, at 7:25 PM, Michael Lucas-Smith wrote:
> WV doesn't show bundles at all sorry. When we sat down with some
> people and tried to explain what they are and how they work, it
> quickly became clear that it was easier to have just the one concept
> for WV - packages. We may put some effort in to hiding bundles but
> providing their same behavior down the road - but not in 1.0 or 1.1.

Thanks! That makes sense. One more question if I could.. If I create
an app from scratch I can edit it, add classes, etc all via the web
interface. I've got my namespace setup, the main part of the app has
a property indicating it's an application and I've even set the
default theme in the properties as well but it still does not show up
anywhere via the web portion of WV -- I'm not completely sure if it
should or not. Am I missing the boat on something or perhaps my app
is still deficient in some way or another.. ?

Sorry.. Still feeling like a bit of a WV newbie..

-- Rick

[Michael Lucas-Smith]

On 5/3/10 9:29 PM, Rick Flower wrote:
> On May 3, 2010, at 7:25 PM, Michael Lucas-Smith wrote:
>> WV doesn't show bundles at all sorry. When we sat down with some
>> people and tried to explain what they are and how they work, it
>> quickly became clear that it was easier to have just the one concept
>> for WV - packages. We may put some effort in to hiding bundles but
>> providing their same behavior down the road - but not in 1.0 or 1.1.
>
> Thanks! That makes sense. One more question if I could.. If I create
> an app from scratch I can edit it, add classes, etc all via the web
> interface. I've got my namespace setup, the main part of the app has
> a property indicating it's an application and I've even set the
> default theme in the properties as well but it still does not show up
> anywhere via the web portion of WV -- I'm not completely sure if it
> should or not. Am I missing the boat on something or perhaps my app
> is still deficient in some way or another.. ?
>
> Sorry.. Still feeling like a bit of a WV newbie..

The only thing that filters stuff in the WV front page (which we call
the launcher page) is the #application property being true (not the
string, the boolean object). That's the only piece of secret sauce you
need. I can't imagine why it wouldn't show up after setting that property.

Michael

[Rick Flower]

On Mon, 03 May 2010 23:35:25 -0700, Michael Lucas-Smith
<michael.l...@gmail.com> wrote:
> The only thing that filters stuff in the WV front page (which we call
> the launcher page) is the #application property being true (not the
> string, the boolean object). That's the only piece of secret sauce you
> need. I can't imagine why it wouldn't show up after setting that
property.

Michael,

Ok.. Solved it.. Based on your comment and your earlier comment about
WV not really knowing much about bundles (for the web side of the world),
I realized that the properties I setup the other day are all on the bundle
and not the main package within the bundle.. Once I added a new
#application
property to the main package within the bundle then my application was
listed
on the launcher page..

YAY!!! Thanks!!