Re: Chatting options

http://mibbit.com/ is very good tool for chatting in IRC.

Also, I experimented with Jabber and iCMS. I think is better solution. Because You can chat by using own gmail account. However I wasn't succefull. Frameworks that use Jabber are not very easy to understand :(

Topic


Re: Chatting options

I considered IRC as well, but web-based chat seemed easier to find php-based clients for.

The downside is that you need to have specific sofware installed, so from that point of view, IRC is not better than skype.

I want to concentrate things as much as possible on the website. If there is a good PHP IRC client available somewhere, that would be a perfect match.

I'll see if I find one that is easy to setup. Does anyone has experience with a specific web-based client or library perhaps?

Me on Ohloh

Topic


Re: Chatting options

I think IRC is much more easier. You can setup in a lot of programs, like Thunderbird, Pidgin or else.

You need enter a user name, a server (chat.freenode.net) and the room name #impresscms

The benefit is, it's works on any platforms.

Topic


Chatting options

While Skype is a nice short-term solution, it has its drawbacks. Not everybody uses Skype, and Skype was conceived to make calls, and that's what it does best.

i'm looking for a web-based (free)chat application that we can use on our servers to host discussions on.

We have dhchat in the addons, but it's old and unsupported, so I'm not sure if we should risk it on our servers.

I also found phpfreechat, ajaxchat and phpopenchat. I'm trying out the first 2, as the last one had a latest release in 2005.

Any other tools that can be installed on our current PHP server you know of?

Me on Ohloh

Topic


Re: Sourcetree is now available for windows

Looks interesting, I'll give it a go and see if it works for me. I tried SmartGit, but I couldn't really get the hang of it.

At the moment, I'm just managing my Git and Svn repositories in PhpStorm, for which we have a project license by the way. So if any developers (theme/code) want to use it, let me know and I'll pass on the license details.

Me on Ohloh

Topic


Sourcetree is now available for windows

  • 2013/5/6 19:36:24
  • Will

My favorite GIT client is now available on WIndows if you are unhappy with yours you should give this one a go. I use it on Mac everyday and it is really nice.

http://www.sourcetreeapp.com/

Here is the introduction post:
http://blog.sourcetreeapp.com/2013/03/19/introducing-sourcetree-for-windows-a-free-desktop-client-for-git/

Topic


Re: Google Reader will go, alternatives?

RSSowl

or if you use thunderbird, then the bamboo addon is great.

Live as if you were to die tomorrow, Learn as if you were to live forever

The beauty of a living thing is not the atoms that go into it, but the way those atoms are put together!
Topic


Re: Google Reader will go, alternatives?

If you have an Android phone or tablet, look no further than BeyondPod. It's not free but it is cheap and worth every cent.

Topic


Google Reader will go, alternatives?

I know Google is trying to get everyone on Google+, but I like to have the focused content that I assembled on my Google Reader.

I had a look at pulse, but that's a huge mess (can't find how to import my opml file with feeds). On top of that, rumour is that pulse could besnapped up by linkedin, so the continuity of that service isn't guaranteed either.
Digg, itself a resurrected service, confirmed it is building a replacement RSS reader at the moment.

Does the demise of Google Reader bother you, or will life go on without it? What are your strategies to cope?

Me on Ohloh

Topic


Re: PyroCMS vs ImpressCMS

  • 2013/3/12 11:57:27
  • david

Quote:


Madfish wrote:
I generally agree with Will, but some ideas:

* Can we put together a 1.3 compatible/maintained module pack, and make it available either as part of the core system download (best) or include a link to it on the downloads page / get it now box so people can find it easily?


I've promised this before - i'd like to speak with 63rd from the German forum and see what we can do on this.

Quote:


* Re. nice URLs, this should be fairly easy to implement, depending on "how nice" you wanted them. It could probably be done via a very simple module and index redirect, I will start a new thread on that one shortly.


Excellent - there's been a few more bits of information since your post, including about Symfony 2 routing - which could be worth investigating as well!

Quote:


* Re. integrating content, a single core publishing interface would be great and would certainly help with nice URLs and site wide tagging, although it might be a lot of work.


I think this would be easier when the module pack is done - but agreed

Quote:


* Re. editors, this is another of my bugbears but if a common hook system is developed I'll try (no promises) to integrate a WYSIWYM editor that ties users down to a range of preset styles, rather than letting them rampage with a wild selection of font sizes and colours.


Definately worth speaking with McDonald about his great Tiny work

Quote:


* Re. site redesign, I would be very happy to help with this, although I'm not sure how compatible my ideas are with everyone else (eg. roll sites into one). If I get involved I will want to change things wah ha haaaaa :)


Give me or David a shout when our time zones match - and that goes for anyone else as well!

Topic


Re: old editor settings

  • 2013/3/10 7:46:25
  • david

Yes, I think this could certainly do with being removed.

Even if, we simply remove the option being visible to begin with, and remove the values post 2.0 - as it would give chance for people to have their content updated for a new editor.

Topic


Re: old editor settings

So if I understand it right, it could very well be removed in the core for 2.0?

We'll need to see if a one-time treatment is needed on upgrade of an existing site.

Me on Ohloh

Topic


Re: old editor settings

Do linebreak goes back to having a dhtml editor and wysiwyg editors and does go back to XOOPS, when wysiwyg integration was being added through Frameworks.

Christian Web Resources
Facebook
Topic


Re: old editor settings

  • 2013/3/5 13:18:05
  • david

I think some of the editors - FCKeditor if I recall - generate extra returns in their generated html.

This is to stop it ... I think.

Topic


old editor settings

As mentioned in the topic http://community.impresscms.org/modules/newbb/viewtopic.php?post_id=48002#forumpost48002 by @bleekk, our modules still offer several options that date back from the Xoops time.

* Enable Smiley Icons
* Enable ICMS codes
* Enable Linebreaks

The first 2 options look to me like config options for the editor in combination with page and user group.
The 'Enable Linebreaks' seems a bit outdated. Does anyone know what it does exactly, and if it still makes sense to keep it?

Me on Ohloh

Topic


Re: PyroCMS vs ImpressCMS

I generally agree with Will, but some ideas:

* Can we put together a 1.3 compatible/maintained module pack, and make it available either as part of the core system download (best) or include a link to it on the downloads page / get it now box so people can find it easily?

* Re. nice URLs, this should be fairly easy to implement, depending on "how nice" you wanted them. It could probably be done via a very simple module and index redirect, I will start a new thread on that one shortly.

* Re. integrating content, a single core publishing interface would be great and would certainly help with nice URLs and site wide tagging, although it might be a lot of work.

* Re. editors, this is another of my bugbears but if a common hook system is developed I'll try (no promises) to integrate a WYSIWYM editor that ties users down to a range of preset styles, rather than letting them rampage with a wild selection of font sizes and colours.

* Re. site redesign, I would be very happy to help with this, although I'm not sure how compatible my ideas are with everyone else (eg. roll sites into one). If I get involved I will want to change things wah ha haaaaa :)

Topic


Re: PyroCMS vs ImpressCMS

Here are some points that I personally think should be changed/improved.

1. remove all icms/xoops related code/options from the comments and all other places where it shows up. Remove it from the core completely.


2. Remove banners and profile modules from the download package.
Instead of providing it in the donwload sell it big on the icms homepage. Make a big banner where you show profile module as an extra module that is great and that every one can donwload for free.

3. There is no webpage without content. So integrate the content module in icms. Why integrate? Because you can then make a better usability to the user. See 7.

4. Menu management. There is no cms without menu management. Take a menu module and intagrate it. This module has to provide clean html code. Please not too much extras.
Example:

<ul name=“menuname“> <li class=“first“><a href=“#“>Link1</a></li> <li><a href=“#“>Link2</a></li> <li><a href=“#“>Link3</a></li> <li><a href=“#“>Link4</a></li> <li class=“last“><a href=“#“>Link5</a></li> </ul>

Please do not provide any templates for the menu. Let the theme designers do that for their themes!

5. There must be a folder/files/media management. Creating folder and upload files per d&d must be possible. Someting like elFinder debianus has done. Modules can then easily use this media for example a gallery or a slider module.

6. Decide for one editor! But please choose a modern one. Design/Look is a important selling point. Use this editor in all modules with content.
For comments make a custom small editor with may be 4 possiblities: bold, underline, insert link, insert link for image. That's it.

7. Make the backend easier to use.
Make the most important sections easy to reach.

Overall there are couple of options that need to be deleted.

8. Make html purifier default disabled. Make a warning to use purifier if the site is a community website! One thing that I really hate is when my code or format is changed without knowing why.

9. Nice URLs

10. Redesign of the icms homepage. It is nice to have news on the frontpage but it would be better to show the most important selling points!
Make the important points big on the frontpage: SECURE, PROFILES, 1000 THEMES, …..

free impresscms themes
Topic


Re: PyroCMS vs ImpressCMS

Usability seems to be one of the key things in the 2.0 branch - so myself I'm certainly in favour of it being done.

Is it something that would be easier to do after the Javascript side is completed?

Topic


Re: PyroCMS vs ImpressCMS

If we want to pull this off, we will need more active developers that contribute to the core. This is a timing isue : either we wait another year for these things to be added/rewritten, either we do it incrementally in 2.0, 2.1, 2.2, ... but with a strict roadmap what will be included in what.
This also is with the assumption that no more work is done on 1.3.x, because that would dilute resources even more.

Me on Ohloh

Topic


Re: PyroCMS vs ImpressCMS

  • 2013/3/1 11:28:21
  • Will

Precisely.

I think that ICMS 2 should be held off until we fix these problems. It is a major milestone release - and this is the best possible time to re-imagine and reinvest in the system.

If we let it go past 2.0 then we will get back into the same broken record we have been in for years (compatibility/upgrade/etc)

Now is the time, if we are going to invest this much effort in 2.0 - we should launch it with our best foot forward.

Topic



 Top