| Re: [paho-dev] Website updates |
Thanks Roger, that looks great.
Good spot on the m2m/iot change. I'll update that and add your page when I get in front of my laptop.
Nick
Hi Nick,
How about this?
I've changed m2m.eclipse.org to iot.eclipse.org - we should make that
change universally.
Cheers,
Roger
On Wed, Mar 19, 2014 at 9:02 PM, Nicholas O'Leary <nick.oleary@xxxxxxxxx> wrote:
> Hello Paho Committers.
>
> I've now pushed the new website to: http://eclipse.org/paho/new
>
> I have done the page for the JS client to get the ball rolling - but will
> need input from the rest of you for the other clients/utilities we have.
>
> You can see the list of clients/utilities that I was aware of when I put the
> new page together a month ago -
> http://eclipse.org/paho/new/#getting-started. Looking at the list now I see
> ObjC client is missing - any others that need to be there?
>
> We need, at a bare minimum, a place holder page for everything we have that
> includes:
> - a link to its source repository
> - where appropriate, how to build it
> - a minimal hello world example
>
> Over time, we can flesh out these pages with more content as is appropriate
> for each one. But I don't want the desire to create comprehensive pages get
> in the way of getting something up.
>
> I'm leaving it to the logical 'owners' of each client/utility to step up and
> add their page. I would like to get them done in the next two weeks - please
> can you reply to this mail to identify which pages you're signing up to do.
> That way we can figure out the gaps and get them covered.
>
>
> Thanks,
> Nick
>
>
> On 4 February 2014 08:12, Roger Light <roger@xxxxxxxxxx> wrote:
>>
>> Hi Nick,
>>
>> I think it's a definite improvement.
>>
>> As much as a memo for myself, standard pydoc generated html can be
>> obtained using:
>>
>> pydoc -w <path/to/client.py>
>>
>> This produces... interesting results:
>> http://h.ral.me/python/client.html that don't *quite* :) fit in with
>> your theme and, hurrah, doesn't make use of CSS (there is an open bug
>> on the issue here: http://bugs.python.org/issue10716 )
>>
>> Cheers,
>>
>> Roger
>>
>>
>> On Sat, Feb 1, 2014 at 11:17 PM, Nicholas O'Leary <nick.oleary@xxxxxxxxx>
>> wrote:
>> > Hi,
>> >
>> > as mentioned on the Paho call recently, I've begun working on a refresh
>> > of
>> > the Paho website.
>> >
>> > The intention is to have dedicated pages for each component that
>> > includes
>> > download links, getting-started guides, how-to build etc - something
>> > that is
>> > long overdue.
>> >
>> > I'll be looking to the owners of each component to help out once I've
>> > got a
>> > bit more of it in place. The goal is for consistency. I'm not so worried
>> > about getting auto-generated client docs looking the same (is the
>> > pydoc/jsdoc/javadoc stuff) but at the very least the landing pages for
>> > the
>> > clients need to be consistent in look and content.
>> >
>> > I am still working on an example component page (based on the _javascript_
>> > client, hence the rabbit hole of refactoring I emailed about earlier),
>> > but I
>> > have updated the main page. You can see it here:
>> > http://foo.knolleary.net/paho/
>> >
>> > Let me know what you think.
>> >
>> >
>> > Nick
>> >
>> >
>> > _______________________________________________
>> > paho-dev mailing list
>> > paho-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/paho-dev
>> >
>> _______________________________________________
>> paho-dev mailing list
>> paho-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/paho-dev
>
>
>
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/paho-dev
>
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev