Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - interjinn

Pages: [1] 2 3
1
Feature requests / Re: Is Feng Office going anywhere?
« on: April 13, 2010, 05:25:23 pm »
I was referring to the following thread:

    http://forums.fengoffice.com/index.php?topic=273.0

But I'll yield to your argument of not wanting to raise expectations :)

2
Feature requests / Re: Is Feng Office going anywhere?
« on: April 13, 2010, 04:06:33 pm »
@Interjinn & Gman: Both "features" are not only good suggestions, but already on our "imaginary roadmap". Both make total sense, and should be making their way into future versions, hopefully very soon.

That's great news... and now --since we have your attention-- any hints on what the feature is like that was hinted about in another thread with respect to "folders" for documents?  ;D

3
Feature requests / Re: Is Feng Office going anywhere?
« on: April 13, 2010, 02:10:19 pm »
I can see your perspective now that you explain it. I guess it depends on your use-case. For instance it sounds like your use case is site based and what features should be available to those site trees (if I understand your explanation correctly). Whereas my use-case is client oriented with features being enabled/disabled depending on the client. Clients in my case would find it odd for features to pop in and out of existence depending on what workspace they click on  ;D

4
Feature requests / Re: Is Feng Office going anywhere?
« on: April 13, 2010, 01:36:06 pm »
Hmmmm... workspace configuraton of modules seems kind of weird since modules would activate/deactivate depending on the active workspace alone. I imagined a better system of module configuration (enable/disable) being linked to the permissions management system. That way you can enable/disabled modules for specific users or, as I prefer, by group.

5
Development / Re: Adding document to workspace via external app.
« on: April 02, 2010, 01:15:18 pm »
I completed the functionality the hard way by directly populating the appropriate repository directory and updating the database tables and it works great. However, a webservice would be a much more appropriate solution. Do you know if there is any documentation for the web services?

6
Development / Adding document to workspace via external app.
« on: February 15, 2010, 03:02:49 am »
I'm looking to connect a website document upload form to a specific user/workspace in Feng Office. I have already resolved the necessary database gymnastics necessary to make this work the hard way; however, I was wondering if there was a way within Feng Office to do this easily. The external application is my own InterJinn framework and it plays nicely with other frameworks so it can load the Feng Office system without problems... the question is if there's a simple one liner or something that would leverage Feng's internal system to post the file to a workspace. Preferrably with support for username (or user ID), and workspace path (or workspace ID)... even if it's just setting some environment variables to simulate a logged in user. If not, I could always add such a function to Feng and create a patch  ;D

7
Development / Re: http and https support in the config.php
« on: February 13, 2010, 07:34:28 pm »
Actually, now that I think of it, I can't remember if Feng does the redirect for me or not if I set the URL to have https... I did this when I first started using it... so maybe it's unnecessary :)

8
Development / Re: http and https support in the config.php
« on: February 13, 2010, 07:33:00 pm »
I prefer to force access to HTTPS so that it's guaranteed to be over a secure connection:

Code: [Select]
    if( !isset( $_SERVER['HTTPS'] ) || $_SERVER['HTTPS'] !== 'on' )
    {
        $url = 'https://'.$_SERVER['SERVER_NAME'].$_SERVER['REQUEST_URI'];
        header( 'Location: '.$url );
        exit();
    }

9
How To's / Re: How to tell what users are currently logged in?
« on: February 13, 2010, 12:42:10 am »
I believe this information is already being logged. An easy way to get this information in the current Feng Office is to create a report against the user's module:

    Reporting => Users => + Add a Custom Report

Order by [ Last Activity ] [ Descending ]

Columns to print:

    Company
    Username
    Display name
    Last login
    Last activity

Actually... I just looked at my report, and it looks like the "Last Activity" field is only updates at login time since it remains the same as "Last login", in fact the same is true of "Last visit" also.

Maybe it's fixed in 1.6.2 since I'm only in 1.6.1 :)

10
Feature requests / Re: Is Feng Office going anywhere?
« on: February 13, 2010, 12:22:45 am »
Feng Office benefits both a community and the Feng Office business. It benefits the community because as many of us know, it costs nothing for us to download what Feng Office has brought us so far. It benefits Feng Office because they can sell services and support around the product that they freely give away. In this way the relationship is symbiotic. This has several advantages over a purely community based scenario. For instance, Feng Office has said they have a dedicated team of payed employees whose job it is to fix bugs, add features, engage the community, and polish the software. This ensures resources are allocated regardless of whether the community has gained traction yet, additionally, it provides a control center for any direction the project may take, puts a face on the project for interested businesses, and adds a level of seriousness that can be lacking in purely community efforts. This obviously has a cost to Feng Office that they surely would like to regain over time; however, on the flip side, those with skill can download the software, for free, and use it as they please. The community is in no way obligated to pay for services, pay to add features, or to even like the Feng team, but for the mutual benefit of everyone, skilled community members, or businesses with skilled employees, will usually pass back bug fixes, code enhancements, and even features so that the upstream maintenance of their customizations will be simplified when new releases become available. Additionally, when many users try out alpha, beta, and RC versions of the software, Feng benefits from a large community of application testers which helps enhance the product's quality since most of these people will at the very least return feedback. This in turn drives further adoption.

Anyways, I do go on sometimes it seems, but this is how I've come to understand open source and the commercialization of open source software over the years. As it stands many commercial entities are certainly profiting from Feng Office (I am), and I see no reason why Feng Office shouldn't also profit. If Feng Office can improve their community engagement element and better facilitate contributions, I think they may be on the cusp of a snowball effect.

11
Feature requests / Re: Is Feng Office going anywhere?
« on: February 12, 2010, 06:47:32 pm »
Quote
someone has to light a fire under your seat!

It means someone needs to get you moving since nobody stays still long when their bum is on fire  ;D

12
Feature requests / Re: Is Feng Office going anywhere?
« on: February 12, 2010, 05:15:16 pm »
Thank you Conrado for the well written feedback.

13
Hmmmm... I think I'd prefer to lock a company out of having any control over permissions by default but still allow them to create sub-workspaces for any workspace to which they have access. The sub-workspaces would inherit the permissions of the parent upon creation. I think this should apply to the owner company too. The reasons are as follows:

    - I don't necessarily want my own employees / co-workers to have access to my entire client list

    - Access to permissions allows setting groups access to workspace which could promote another company to the workspace

    - It's very useful for a company to have the ability to organize their own information

I think this really requires extra settings when granting user/group permissions:

    - Can manage workspaces
      Allow user to create workspaces but not at root level and no editing permissions

    - Can create root workspace
       Allow user to create workspace at the root level (I'd prefer only sub-workspaces for 99% of companies)

    - Can manage workspace permissions
      Allow user to manage the workspace permissions but only on a user basis within their own company.

    - Can manage extended workspace permissions
      Allow user to manage any permissions for the workspace.

I don't know about other people, but I generally revoke user based permissions except to personal space, and assign all users to one or more groups that provide workspace access. I still feel there's something lacking in the above... unfortunately I think it's company level group permissions and the ability to revoke permissions since as it stands it makes sense for only the owner company to have group level permissions control... but with company level groups then we could have the following:

    - Company A users are all added as members of Group A and Group B

    - Group A permissions

           Access to workspace "Root => Company A"

    - Group B permissions

           Access to workspace "Root => Company B"
   
So far this means anyone in Company A has access to these workspaces. Now at the company level we create company level groups:

    - Group C:A

            Revoke Master Permissions
            Access to workspace "Root => Company A"

    - Group C:B

            Revoke Master Permissions
            Access to workspace "Root => Company B"

Then the company could assign their own users within these company level groups to restrict and mix/match their own permissions. So a user added to Group C:A would only have access to "Root => Company A" and a user added to Group C:B would only have access to "Root => Company B" but a user added tp Group C:A and Group C:B would have access to either. And of course the user could always be individually granted access regardless of either level of group permissions. Of course, all this increases the complexity greatly and probably would be heavy on the server to resolve specific access.

Thoughts?

14
Feature requests / Re: Extend usefulness of USE_COOKIE_PREFIX
« on: February 10, 2010, 02:57:24 am »
Please accept this patch for the above requested change against environment/classes/Cooke.class.php in FengOffice 1.6.2. This makes it easier to connect FengOffice to other PHP applications without worrying about cookie clobbering  ;D

15
Feature requests / Re: Is Feng Office going anywhere?
« on: February 08, 2010, 04:39:00 pm »
*lol* Touché!  ;D

Pages: [1] 2 3